HTTPS Parameters

The Secure Hypertext Transport Protocol (HTTPS) parameters are described in the table below.

HTTPS Parameters

Parameter

Description

'Secured Web Connection (HTTPS)'

configure system > web > secured-connection

[HTTPSOnly]

Defines the HTTP/S application protocol for accessing the device's management interface (Web interface or REST API).

■ [0] HTTP and HTTPS = (Default) Access to the management interface is allowed from HTTP and HTTPS (secured) requests.
■ [1] HTTPS Only = Access to the management interface is allowed only from HTTPS requests (and unencrypted HTTP packets are blocked).
■ [2] HTTPS Redirect = Access to the management interface is allowed only from HTTPS redirect URLs. This is required when using OAuth login authentication with Azure AD, which redirects the user to a URI (device's address) upon successful authentication and authorization.

Note:

■ For the parameter to take effect, a device restart is required.
■ If you configure the parameter to HTTPS Redirect and you're using Single-Sign On (SSO) to the device from OVOC, you must configure OVOC to connect to the device using HTTPS ('Communication Protocol' field set to HTTPS).

configure system > web > https-port

[HTTPSPort]

Defines the local Secured HTTPS port of the device. The parameter allows secure remote device Web- or REST-based management from the LAN. To enable secure Web management from the LAN, configure the desired port.

The valid range is 1 to 65535 (other restrictions may apply within this range). The default port is 443.

Note: For the parameter to take effect, a device restart is required.

'Require Client Certificates for HTTPS connection'

configure system > web > req-client-cert

[HTTPSRequireClientCertificate]

Enables the requirement of client certificates for HTTPS connection.

■ [0] Disable = (Default) Client certificates are not required.
■ [1] Enable = Client certificates are required. The client certificate must be preloaded to the device and its matching private key must be installed on the managing PC. Time and date must be correctly set on the device for the client certificate to be verified.

Note:

■ For the parameter to take effect, a device restart is required.
■ For a description on implementing client certificates, see TLS for Remote Device Management.